We recommend that all AutoDoubler users upgrade to version 1.0.5 or later.
Instructions:
------------
The patcher by default patches the installed copy. It will only prompt you if it can't find the file to patch.
If you want to patch your master disk, follow these directions. Follow them carefully, or you may end up with a disk that won't install.
1. Throw the installed copy of AutoDoubler in the trash. (It's in the Control Panels folder or System Folder).
2. Lock your original master disk.
3. Make a backup copy of your master disk (just in case). Remember to make the name of the backup disk exactly the same as the original disk name.
4. Copy just the AutoDoubler control panel from the master disk to your hard disk.
5. Run the patcher. It will prompt you for the file to patch. Select the AutoDoubler you just copied to your hard disk.
5. Copy the now patched AutoDoubler back to the master disk, then lock the master disk.
6. Run the AutoDoubler installer on the master disk.
FIX/CONFLICT/BUG LIST
--------
4-APR-92
AUTODOUBLER / DISKDOUBLER CONFLICTS DOCUMENT
We are continuously updating this document as we get feedback from our technical support department and users. As a result, we will periodically publish this document to aid you in using AutoDoubler and DiskDoubler. This document supercedes all prior documents.
Many of these "conflicts" do not involve AutoDoubler directly, but AutoDoubler's presence can bring out bugs in other products. We have included such conflicts here for completeness.
DOVE MARATHON 030, PLUS or SE, AD (all versions)
DO NOT RUN AUTODOUBLER WHEN USING A MARATHON ACCELERATOR.
The Marathon accelerator for the Mac SE and MacPlus has a hardware bug that can scramble data. This problem occurs with or without the Marathon software in any of its configurations. Any program that uses certain 68020/68030 instructions and/or addressing modes is affected by the problem. However, most programs are not affected by the problem.
Dove engineering has confirmed the problem (4/7/92) and is working on a hardware fix. Exact details are not yet available, but Dove has said that they will provide some kind of upgrade/fix program for affected users.
Note that this problem is a bug in the Marathon hardware board. It is NOT a bug in AutoDoubler.
The AutoDoubler 1.0.6 installer now refuses to install if a Dove Marathon board is installed.
MAC PORTABLE OR POWERBOOK, AD 1.0-1.0.5
Certain operations on a Portable or PowerBook can cause a bus error (ID=01). (Tech note: Any application that deferences an NIL handle will cause this bus error to happen. A "properly" written application won't dereference NIL, but there are some that do.) Some operations that dereference NIL are: (1) in the system 7 Finder, copying an icon in the Get Info window; (2) opening MacPhoneBook (made by SYNEX) from the Apple menu. Either of these operations in the presence of AutoDoubler will cause a crash or freeze. This problem is resolved in AD 1.0.6.
AUTOMAC III, AD 1.0.5-1.0.6
There is a conflict between AutoDoubler 1.0.5-1.0.6 (not earlier versions) and AutoMac III v2.1. AutoMac III is bundled with MS Word 4.0. When you open a document, it opens fine, but when you quit, the "put-back" copy stays in the AutoDoubler Temporary Items folder until shutdown. Also, AutoMac will not allow AD to perform any background compression. There is no workaround.
ALARMSCLOCK 3.0.1, AD 1.0.5-1.0.6
NOW Utilities AlarmsClock 3.0.1 conflicts with AutoDoubler 1.0.5-1.0.6. It does not conflict with earlier versions of AutoDoubler. The conflict is caused by a bug in AlarmsClock. When the Finder comes up at startup, a watch cursor will appear and never go away. The computer freezes, except for the cursor. Jorg Brown, AlarmsClock author, acknowledges the bug and said that it is fixed in Now Utilities 3.0.2. The only workaround is upgrade to AlarmsClock 3.0.2. (Tech Note: any product that patches WaitNextEvent() will have the same conflict with AlarmsClock.)
VIREX 3.5.1-3.5.2, FILESHARE, AD (all versions)
With both Virex and System 7 FileShare active, Virex tends to lock up the machine. The problem is not caused by AutoDoubler, but the presence of AutoDoubler makes the problem occur more frequently. We have verified that the problem occurs when you attempt to rename a compressed file, though the problem may occur at other times. Microcom, makers of Virex, have acknowledged the bug and have reportedly fixed the problem in Virex 3.6. The interim solution is to turn off either FileShare or Virex.
VIREX (all versions up to 3.6), AD (all versions), DD (all versions)
Virex has a bug that can cause all compressed-file icons to revert back to generic DiskDoubler icons. The problem only occurs if the "Diagnose Files When Opened" is NOT checked in the Virex control panel: If you try to expand a file with DiskDoubler, DDExpand, etc., a system error -50 will result. The solution is to make sure the "Diagnose Files When Opened" setting IS checked. Microcom, makers of Virex, is aware of the bug and will be fixing it in a later revision (probably 3.6.1).
TOPS, AD (all versions)
The conflict causes many different types of file error messages. No data corruption occurs with any of these errors. If users really want to run both TOPS and AD, make sure they load AD _after_ TOPS. Later revisions of AD will automatically install after TOPS. We recommend our users migrate to another type of server software.
HANDOFF 2, FILESHARE, AD (all versions)
With these three items activated, a HandOff 2 bug is activated which causes a system freeze. Fred Hollander, author of HandOff 2, said that the bug will be fixed in the next revision of HandOff 2.
SAM INTERCEPT, AD (all versions)
SAM Intercept can be set to scan inserted floppies. This works fine with AD, as long as all compressed files on the floppy were compressed with AD. If there are files on the floppy that were compressed with DiskDoubler Method A or B or Sigma, AD will attempt to expand those files on disk when SAM scans them. SAM prevents the expanded files from being created, which causes a -36 error message (I/O Errors). There is no workaround.
AD SETTINGS, AD 1.0.4
After a restart, the settings for a particular volume may get reset to the default settings. This is not harmful, only annoying. The bug has been fixed in AD 1.0.5.
EMPOWER, AD 1.0.4 or later
Empower requires that AutoDoubler load after Empower. If AutoDoubler loads first, certain actions like renaming folders may fail. The installer for AD 1.0.5 or later will check for Empower's presence and will force AutoDoubler to load afterward.
MICROPHONE II, AD 1.0-1.0.2
MicroPhone will successfully send AD-compressed files over a modem, but it will send them twice. So the savings of sending a compressed file is nullified by sending the file twice. This conflict has been fixed in AD 1.0.3.
VIREX 3.5.1-3.5.2, DD 3.7.2-3.7.4
If Virex loads before DiskDoubler, a system crash may occur when the Finder attempts to start up. (The reason: Virex counts the number of times the Finder is opened. DD opens the Finder at startup, which increases the count by one. This can cause a crash on some machines in some situations.) The solution is to specify Virex to load last. In the Virex control panel, select "Installation Options", Load Virex INIT: "Last". There is a work-around to this conflict in DiskDoubler 3.7.5. Later revisions of Virex have eliminated this bug, also.
WORD 5.0, AD (all versions)
Word has a Find feature which directly parses the Apple file system's data structures. Those data structures are Apple private data which Apple may change at any time, causing Word 5.0 to break. As a result, Word will not Find compressed documents, unless you ask Word to find documents of any type. We consider this a bug in Word 5.0, so the Find command will not work until (unless) Microsoft fixes the problem. According to a Word 5.0 developer at Microsoft, they will fix this in a later revision.
WORD 5.0, POWERBOOK 170, SYSTEM 7 TUNE-UP
Apparently there is a bug in TuneUp that causes the system to get corrupted when the MS Word installer installs the special math or symbol font into the system (I forget the exact name of the font). Later, MS Word crashes inexplicably, especially when compressed. Solution: After installing Word, Install System 7.0.1 again, then install TuneUp again. Apparently Apple is not being very forthright about admitting to this problem, but it's there. It's not known whether this problem will occur if TuneUp is not installed.
DOUBLEUP COMPRESSION BOARD, AD (all versions), DD 3.7.2 (or later)
This is not a conflict. If a user does not have the DoubleUp board installed and attempts to expand a DoubleUp-compressed file using DD, an "Error 17" message will be generated. If AD attempts to open a DoubleUp file without the board present, AD will generate an error code -20992. DoubleUp must be installed to be able to open a DoubleUp file, so the error messages are correct. To avoid confusion, DD 3.7.3 has a more descriptive error message than "Error 17".
APPLESHARE, DD 3.7.2 or AD 1.0-1.0.2
This conflict only occurs under the following circumstances:
o AppleShare server machine running system 6.0.x
o Client machine running System 7 and either DD 3.7.2 or AD 1.0 (or both)
If the system 7 client attempts to compress files on the AppleShare server, the files will not get compressed. But their type will be changed to DD files. Any attempt to expand them will result in a "file corrupted" error message. The files are not corrupted, and they may be fixed by restoring the original type and creator of the file. This would be a major nuisance for a large number of files, so we consider this a major conflict. DD 3.7.3 and AD 1.0.3 fix the conflict.
CLICK CHANGE, AD (all versions)
These two apparently don't work together in some situations, causing system freezes in the Finder. A number of users reported that loading AD after ClickChange seems to resolve the conflict, but we have not yet verified this. We have tested AD with ClickChange 1.05.2, and we have found no ill side-effects.
DISK EXPRESS II, SYSTEM 6, AD 1.0-1.0.2
Running these two INITs under system 6 will result in a system error "unimplemented trap error" (system error 12), or a DiskExpress error code 2004. The problem occurs when Disk Express 2 calls a system 7 trap when running under system 6. AD 1.0.3 fixes this conflict.
NORTON FILESAVER, AD (all versions)
FileSaver will not work when Personal FileShare is turned on, no matter what other INITs are on. Norton will probably fix this some day. We recommend not running FileSaver in conjunction with AD, as it provides little benefit in the presence of AD and slows the computer down.
NORTON FILESAVER, AD 1.0.4
There is a conflict between FileSaver and AutoDoubler 1.0.4. FileSaver repeatedly complains of an error 95. The solution is to not run FileSaver. We will have a work-around in AutoDoubler 1.0.5 that will at least get around the continuous error reports. We recommend not running FileSaver's deleted file tracking in conjunction with AD, as it always slows the computer down and provides no real benefit in the presence of AD.
SAM, AFTER DARK, AD (all versions)
This is not a conflict, but SAM can make it seem that After Dark has frozen. SAM will put up its warning alert when AD is compressing. The dialog will cause After Dark to APPEAR frozen. Hitting the enter key will get rid of the SAM dialog. Our suggestion: turn off After Dark while AutoDoubler is making its initial compression scan. Use SAM's "Learn" button when the SAM warnings come up. After SAM "learns" about AD, you can turn After Dark back on. NOTE: The same apparent "conflict" will occur with other screen savers and virus checkers, such as Pyro.
GATEKEEPER, AD (all versions)
GateKeeper, a shareware virus protector, is very energetic at keeping things from happening to files. It won't allow AutoDoubler to perform background compression of many types of files. As a result, lots of temporary files will get scattered around the disk. These files start with "1.", "2.", etc. The solution is to stop using GateKeeper until GateKeeper gets fixed. AD 1.0.4 detects GateKeeper interference, displays an alert, and turns off automatic compression. AD 1.0.5 will only do compression in the Finder layer, so GateKeeper users can give the Finder "other" permission and have no further problems.
MPW, AD 1.0
MPW generated I/O errors for certain files it attempted to open. This conflict has been fixed with AD 1.0.1 and later.
M.Y.O.B., AD 1.0-1.0.2
Mind Your Own Business (MYOB) will generate I/O errors for certain files it attempts to open. This conflict has likely been fixed with AD 1.0.3.
DESKWRITER 2.2, DISKDOUBLER 3.7.2
With these two items installed, you will notice strangely shaded icons. Many icons will be shown as black rectangles. Also, when printing to the DeskWriter, an error -48 (duplicate filename) may result. The conflict has been resolved in DD 3.7.3.
FILEMAKER PRO, ANY FILE SERVER, DISKDOUBLER 3.7.2
This is a rather obscure conflict. The following conditions must be met to invoke the problem:
1) A FileMaker Pro database must be on a file server.
2) A DD-compressed file must reside in the same folder as the database.
3) A client who has DD 3.7.2 installed must try to open the database.
If all three of these conditions are met, the database will not be successully opened. The error message will say that the file is open or locked. DD 3.7.3 or later resolves the conflict. [NOTE: Other applications may have the same problem as FileMaker Pro, but that is the only one we know about at this time.]
PRINTMONITOR, AD 1.0-1.0.2
In some situations, PrintMonitor will generate an error message. The most common error message will contain the text "Where:80, Why:-50". The conflict is resolved with AD 1.0.3.
"PRINT DIRECTORY" COMMAND, System 6, AD 1.0-1.0.3
When using the Finder under System 6, choosing the "Print Directory" command will cause a stack overflow error (system error 28). This has been fixed in AD 1.0.4.
TRASH ALIAS, FILESHARE
This is purely a conflict between TrashAlias and FileShare. It occurs in the presence of any other INIT, or no other INITs. If you drag an item to the trash and empty it, the watch cursor will come up and never go away. The solution is to turn off TrashAlias or FileShare.
ON CUE II, AD (any version)
Using OnCue II, under the "Configure..." dialog, inserting a folder into the OnCue II menu as an "OnCue II Folder" can cause a bus error. We have investiagted the problem and believe that it is not caused by AutoDoubler. We are in contact with ICOM to hopefully resolve the problem.
SPEEDYCD, AD (all versions)
SpeedyCD works in conjunction with a CD ROM, making it appear like you can write to the CD. AutoDoubler does not like this. If a user attempts to open a CD containing DD-compressed files, AD will try to expand those files ON THE CD. This attempt will fail with a -36 error. There is no fix or workaround for this problem.
AUTODOUBLER ERROR CODES
These are the internal error codes used by AutoDoubler. They may be displayed in an error alert in some situations.
-22000 the data written was not successfully write-verified
-21000 user aborted the operation
-20999 checksum does not match; the data file is corrupted
-20998 not enough memory is available for expansion
-20997 a magic number field is wrong; the data is corrupted or this is not a
compressed file
-20996 the header for the compressed data is corrupted
-20995 an unknown version of DiskDoubler created the data (might be a
DoubleUp file, and Sigma Hardware INIT is not present)
-20994 the compression algorithm specified in the file is not valid
-20993 not enough stack space; too many levels of recursion
-20992 DoubleUp hardware not installed
-20991 DoubleUp hardware is busy
-20990 problem with the DoubleUp hardware
-20989 no savings were achieved on the file
-20988 internal error (never happens)
-20987 file is already compressed
DOUBLEUP ERROR CODES
These are error codes that pertain to the DoubleUp compression board. DD 3.7.3 or later contain more descriptive messages than just these numbers.
13 The DoubleUp Board is disabled.
14 The Sigma DoubleUp board is busy. Some other process is using it.
15 The Sigma Hardware INIT is busy. Some other process is using it.
16 The Sigma Hardware INIT was given a bad message.
17 The DoubleUp board is missing.
That's all for now. We'll continue to keep you posted of conflicts and their resolutions.
